Self-propelled device for interpreting input from a controller device

ABSTRACT

A self-propelled device operates to interpret an input corresponding to a set of actions that are performed on a controller device.

RELATED APPLICATIONS

This application claims priority to (i) U.S. Provisional PatentApplication Ser. No. 61/430,023, entitled “Method and System forControlling a Robotic Device,” filed Jan. 5, 2011; (ii) U.S. ProvisionalPatent Application Ser. No. 61/430,083, entitled “Method and System forEstablishing 2-Way Communication for Controlling a Robotic Device,”filed Jan. 5, 2011; and (iii) U.S. Provisional Patent Application Ser.No. 61/553,923, entitled “A Self-propelled Device and System and Methodfor Controlling Same,” filed Oct. 31, 2011; all of the aforementionedpriority applications are hereby incorporated by reference in theirrespective entirety.

FIELD OF THE INVENTION

Embodiments described herein generally relate to a self-propelleddevice, and more specifically, to a self-propelled device forinterpreting input from a controller device.

BACKGROUND

Early in human history, the wheel was discovered and human fascinationwith circular and spherical objects began. Humans were intrigued bydevices based on these shapes: as practical transportation andpropulsion, and as toys and amusements. Self-propelled spherical objectswere initially powered by inertia or mechanical energy storage indevices such as coiled springs. As technology has evolved, new ways ofapplying and controlling these devices have been invented. Today,technology is available from robotics, high energy-density batterysystems, sophisticated wireless communication links, micro sensors formagnetism, orientation and acceleration, and widely availablecommunication devices with displays and multiple sensors for input.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic depiction of a self-propelled device, according toone or more embodiments.

FIG. 2A is a schematic depiction of an embodiment comprising aself-propelled device and a computing device, under an embodiment.

FIG. 2B depicts a system comprising computing devices and self-propelleddevices, according to another embodiment.

FIG. 2C is a schematic that illustrates a system comprising a computingdevice and multiple self-propelled devices, under another embodiment.

FIG. 3 is a block diagram illustrating the components of aself-propelled device that is in the form of a robotic, spherical ball,in accordance with an embodiment.

FIGS. 4A, 4B, and 4C illustrate a technique for causing controlledmovement of a spherical self-propelled device, in accordance with one ormore embodiments.

FIG. 5 further illustrates a technique for causing motion of aself-propelled spherical device, according to an embodiment.

FIG. 6 is a block diagram depicting a sensor array and data flow,according to an embodiment.

FIG. 7 illustrates a system including a self-propelled device, and acontroller computing device that controls and interacts with theself-propelled device, according to one or more embodiments.

FIG. 8A illustrates a more detailed system architecture for aself-propelled device and system, according to an embodiment.

FIG. 8B illustrates the system architecture of a computing device,according to an embodiment.

FIG. 8C illustrates a particular feature of code execution, according toan embodiment.

FIG. 8D illustrates an embodiment in which a self-propelled device 800implements control using a three-dimensional reference frame and controlinput that is received from another device that utilizes atwo-dimensional reference frame, under an embodiment.

FIG. 9 illustrates a method for operating a self-propelled device usinga computing device, according to one or more embodiments.

FIG. 10 illustrates a method for operating a computing device incontrolling a self-propelled device, according to one or moreembodiments.

FIG. 11A through FIG. 11C illustrate an embodiment in which a userinterface of a controller is oriented to adopt an orientation of aself-propelled device, according to one or more embodiments.

FIG. 11D illustrates a method for calibrating a user-interface fororientation based on an orientation of the self-propelled device,according to an embodiment.

FIG. 12A and FIG. 12B illustrate different interfaces that can beimplemented on a controller computing device.

FIG. 13A through FIG. 13C illustrate a variety of inputs that can beentered on a controller computing device to operate a self-propelleddevice, according to an embodiment.

FIG. 14A illustrates a system in which a self-propelled device isrepresented in a virtual environment while the self-propelled deviceoperates in a real-world environment, under an embodiment.

FIG. 14B and FIG. 14C illustrate an application in which aself-propelled device acts as a fiducial marker, according to anembodiment.

FIG. 15 illustrates an interactive application that can be implementedfor use with multiple self-propelled devices, depicted as spherical orrobotic balls, under an embodiment.

FIGS. 16A and 16B illustrate a method of collision detection, accordingto an embodiment.

DETAILED DESCRIPTION

In an embodiment, a self-propelled device is provided, which includes adrive system, a spherical housing, and a biasing mechanism. The drivesystem includes one or more motors that are contained within thespherical housing. The biasing mechanism actively forces the drivesystem to continuously engage an interior of the spherical housing inorder to cause the spherical housing to move.

According to another embodiment, a self-controlled device maintains aframe of reference about an X-, Y- and Z-axis. The self-controlleddevice processes an input to control the self-propelled device, theinput being based on the X- and Y-axis. The self-propelled device iscontrolled in its movement, including about each of the X-, Y- andZ-axes, based on the input.

Still further, another embodiment provides a system that includes acontroller device and a self-propelled device. The self-propelled deviceis operable to move under control of the controller device, andmaintains a frame of reference about an X-, Y- and Z-axis. Thecontroller device provides an interface to enable a user to entertwo-dimensional control input about the X- and Y-axes. Theself-propelled device processes the control input from the controllerdevice in order to maintain control relative to the X-, Y- and Z-axes.

According to another embodiment, a self-propelled device determines anorientation for its movement based on a pre-determined reference frame.A controller device is operable by a user to control the self-propelleddevice. The controller device includes a user interface for controllingat least a direction of movement of the self-propelled device. Theself-propelled device is configured to signal the controller deviceinformation that indicates the orientation of the self-propelled device.The controller device is configured to orient the user interface, basedon the information signaled from the self-propelled device, to reflectthe orientation of the self-propelled device.

According to another embodiment, a controller device is provided for aself-propelled device. The controller device includes one or moreprocessors, a display screen, a wireless communication port and amemory. The processor operates to generate a user interface forcontrolling at least a directional movement of the self-propelleddevice, receive information from the self-propelled device over thewireless communication port indicating an orientation of theself-propelled device, and configure the user interface to reflect theorientation of the self-propelled device.

In still another embodiment, a self-propelled device includes a drivesystem, a wireless communication port, a memory and a processor. Thememory stores a first set of instructions for mapping individual inputsfrom a first set of recognizable inputs to a corresponding command thatcontrols movement of the self-propelled device. The processor (orprocessors) receive one or more inputs from the controller device overthe wireless communication port, map each of the one or more inputs to acommand based on the set of instructions, and control the drive systemusing the command determined for each of the one or more inputs. Whilethe drive system is controlled, the processor processes one or moreinstructions to alter the set of recognizable inputs and/or thecorresponding command that is mapped to the individual inputs in the setof recognizable inputs.

Still further, embodiments enable a controller device to include anobject or virtual representation of the self-propelled device.

TERMS

As used herein, the term “substantially” means at least almost entirely.In quantitative terms, “substantially” means at least 80% of a statedreference (e.g., quantity of shape).

In similar regard, “spherical” or “sphere” means “substantiallyspherical.” An object is spherical if it appears as such as to anordinary user, recognizing that, for example, manufacturing processesmay create tolerances in the shape or design where the object isslightly elliptical or not perfectly symmetrical, or that the object mayinclude surface features or mechanisms for which the exterior is notperfectly smooth or symmetrical.

Overview

Referring now to the drawings, FIG. 1 is a schematic depiction of aself-propelled device, according to one or more embodiments. Asdescribed by various embodiments, self-propelled device 100 can beoperated to move under control of another device, such as a computingdevice operated by a user. In some embodiments, self-propelled device100 is configured with resources that enable one or more of thefollowing: (i) maintain self-awareness of orientation and/or positionrelative to an initial reference frame after the device initiatesmovement; (ii) process control input programmatically, so as to enable adiverse range of program-specific responses to different control inputs;(iii) enable another device to control its movement using software orprogramming logic that is communicative with programming logic on theself-propelled device; and/or (iv) generate an output response for itsmovement and state that it is software interpretable by the controldevice.

In an embodiment, self-propelled device 100 includes severalinterconnected subsystems and modules. Processor 114 executesprogrammatic instructions from program memory 104. The instructionsstored in program memory 104 can be changed, for example to addfeatures, correct flaws, or modify behavior. In some embodiments,program memory 104 stores programming instructions that arecommunicative or otherwise operable with software executing on acomputing device. The processor 114 is configured to execute differentprograms of programming instructions, in order to after the manner inwhich the self-propelled device 100 interprets or otherwise responds tocontrol input from another computing device.

Wireless communication 110, in conjunction with communication transducer102, serves to exchange data between processor 114 and other externaldevices. The data exchanges, for example, provide communications,provide control, provide logical instructions, state information, and/orprovide updates for program memory 104. In some embodiments, processor114 generates output corresponding to state and/or position information,that is communicated to the controller device via the wirelesscommunication port. The mobility of the device makes wired connectionsundesirable; the term “connection” should be understood to mean alogical connection made without a physical attachment to self-propelleddevice 100.

In one embodiment, wireless communication 110 implements the BLUETOOTHcommunications protocol and transducer 102 is an antenna suitable fortransmission and reception of BLUETOOTH radio signals. Other wirelesscommunication mediums and protocols may also be used in alternativeimplementations.

Sensors 112 provide information about the surrounding environment andcondition to processor 114. In one embodiment, sensors 112 includeinertial measurement devices, including a 3-axis gyroscope, a 3-axisaccelerometer, and a 3-axis magnetometer. According to some embodiments,the sensors 114 provide input to enable processor 114 to maintainawareness of the device's orientation and/or position relative to theinitial reference frame after the device initiates movement. In variousembodiments, sensors 112 include instruments for detecting light,temperature, humidity, or measuring chemical concentrations orradioactivity.

State/variable memory 106 stores information about the present state ofthe system, including, for example, position, orientation, rates ofrotation and translation in each axis. The state/variable memory 106also stores information corresponding to an initial reference frame ofthe device upon, for example, the device being put in use (e.g., thedevice being switched on), as well as position and orientationinformation once the device is in use. In this way, some embodimentsprovide for the device 100 to utilize information of the state/variablememory 106 in order to maintain position and orientation information ofthe device 100 once the device starts moving.

Clock 108 provides timing information to processor 114. In oneembodiment, clock 108 provides a timebase for measuring intervals andrates of change. In another embodiment, clock 108 provides day, date,year, time, and alarm functions. In one embodiment clock 108 allowsdevice 100 to provide an alarm or alert at pre-set times.

Expansion port 120 provides a connection for addition of accessories ordevices. Expansion port 120 provides for future expansion, as well asflexibility to add options or enhancements. For example, expansion port120 is used to add peripherals, sensors, processing hardware, storage,displays, or actuators to the basic self-propelled device 100.

In one embodiment, expansion port 120 provides an interface capable ofcommunicating with a suitably configured component using analog ordigital signals. In various embodiments, expansion port 120 provideselectrical interfaces and protocols that are standard or well-known. Inone embodiment, expansion port 120 implements an optical interface.Exemplary interfaces appropriate for expansion port 120 include theUniversal Serial Bus (USB), Inter-Integrated Circuit Bus (I2C), SerialPeripheral Interface (SPI), or ETHERNET.

Display 118 presents information to outside devices or persons. Display118 can present information in a variety of forms. In variousembodiments, display 118 can produce light in colors and patterns,sound, vibration, music, or combinations of sensory stimuli. In oneembodiment, display 118 operates in conjunction with actuators 126 tocommunicate information by physical movements of device 100. Forexample, device 100 can be made to emulate a human head nod or shake tocommunicate “yes” or “no.”

In one embodiment, display 118 is an emitter of light, either in thevisible or invisible range. Invisible light in the infrared orultraviolet range is useful, for example to send information invisibleto human senses but available to specialized detectors. In oneembodiment, display 118 includes an array of Light Emitting Diodes(LEDs) emitting various light frequencies, arranged such that theirrelative intensity is variable and the light emitted is blended to formcolor mixtures.

In one embodiment, display 118 includes an LED array comprising severalLEDs, each emitting a human-visible primary color. Processor 114 variesthe relative intensity of each of the LEDs to produce a wide range ofcolors. Primary colors of light are those wherein a few colors can beblended in different amounts to produce a wide gamut of apparent colors.Many sets of primary colors of light are known, including for examplered/green/blue, red/green/blue/white, and red/green/blue/amber. Forexample, red, green and blue LEDs together comprise a usable set ofthree available primary-color devices comprising a display 118 in oneembodiment. In other embodiments, other sets of primary colors and whiteLEDs are used.

In one embodiment, display 118 includes an LED used to indicate areference point on device 100 for alignment.

Power 124 stores energy for operating the electronics andelectromechanical components of device 100. In one embodiment, power 124is a rechargeable battery. Inductive charge port 128 allows forrecharging power 124 without a wired electrical connection. In oneembodiment, inductive charge port 128 accepts magnetic energy andconverts it to electrical energy to recharge the batteries. In oneembodiment, charge port 128 provides a wireless communication interfacewith an external charging device.

Deep sleep sensor 122 puts the self-propelled device 100 into a verylowpower or “deep sleep” mode where most of the electronic devices use nobattery power. This is useful for long-term storage or shipping.

In one embodiment, sensor 122 is non-contact in that it senses throughthe enclosing envelope of device 100 without a wired connection. In oneembodiment, deep sleep sensor 122 is a Hall Effect sensor mounted sothat an external magnet can be applied at a pre-determined location ondevice 100 to activate deep sleep mode.

Actuators 126 convert electrical energy into mechanical energy forvarious uses. A primary use of actuators 126 is to propel and steerself-propelled device 100. Movement and steering actuators are alsoreferred to as a drive system or traction system. The drive system movesdevice 100 in rotation and translation, under control of processor 114.Examples of actuators 126 include, without limitation, wheels, motors,solenoids, propellers, paddle wheels and pendulums.

In one embodiment, drive system actuators 126 include two parallelwheels, each mounted to an axle connected to an independentlyvariable-speed motor through a reduction gear system. In such anembodiment, the speeds of the two drive motors are controlled byprocessor 114.

However, it should be appreciated that actuators 126, in variousembodiments, produce a variety of movements in addition to merelyrotating and translating device 100. In one embodiment, actuators 126cause device 100 to execute communicative or emotionally evocativemovements, including emulation of human gestures, for example, headnodding, shaking, trembling, spinning or flipping. In some embodiments,processor coordinates actuators 126 with display 118. For example, inone embodiment, processor 114 provides signals to actuators 126 anddisplay 118 to cause device 100 to spin or tremble and simultaneouslyemit patterns of colored light. In one embodiment, device 100 emitslight or sound patterns synchronized with movements.

In one embodiment, self-propelled device 100 is used as a controller forother network-connected devices. Device 100 contains sensors andwireless communication capability, and so it can perform a controllerrole for other devices. For example, self-propelled device 100 can beheld in the hand and used to sense gestures, movements, rotations,combination inputs and the like.

FIG. 2A is a schematic depiction of an embodiment comprising aself-propelled device and a computing device, under an embodiment. Morespecifically, a self-propelled device 214 is controlled in its movementby programming logic and/or controls that can originate from acontroller device 208. The self-propelled device 214 is capable ofmovement under control of the computing device 208, which can beoperated by a user 202. The computing device 208 can wirelesslycommunicate control data to the self-propelled device 214 using astandard or proprietary wireless communication protocol. In variations,the self-propelled device 214 may be at least partially self-controlled,utilizing sensors and internal programming logic to control theparameters of its movement (e.g., velocity, direction, etc.). Stillfurther, the self-propelled device 214 can communicate data relating tothe device's position and/or movement parameters for the purpose ofgenerating or alternating content on the computing device 208. Inadditional variations, self-propelled device 214 can control aspects ofthe computing device 208 by way of its movements and/or internalprogramming logic.

As described herein, the self-propelled device 214 may have multiplemodes of operation, including those of operation in which the device iscontrolled by the computing device 208, is a controller for anotherdevice (e.g., another self-propelled device or the computing device208), and/or is partially or wholly self-autonomous.

Additionally, embodiments enable the self-propelled device 214 and thecomputing device 208 to share a computing platform on which programminglogic is shared, in order to enable, among other features, functionalitythat includes: (i) enabling the user 202 to operate the computing device208 to generate multiple kinds of input, including simple directionalinput, command input, gesture input, motion or other sensory input,voice input or combinations thereof; (ii) enabling the self-propelleddevice 214 to interpret input received from the computing device 208 asa command or set of commands; and/or (iii) enabling the self-propelleddevice 214 to communicate data regarding that device's position,movement and/or state in order to effect a state on the computing device208 (e.g., display state, such as content corresponding to acontroller-user interface). Embodiments further provide that theself-propelled device 214 includes a programmatic interface thatfacilitates additional programming logic and/or instructions to use thedevice. The computing device 208 can execute programming that iscommunicative with the programming logic on the self-propelled device214.

According to embodiments, the self-propelled device 214 includes anactuator or drive mechanism causing motion or directional movement. Theself-propelled device 214 may be referred to by a number of relatedterms and phrases, including controlled device, robot, robotic device,remote device, autonomous device, and remote-controlled device. In someembodiments, the self-propelled device 214 can be structured to move andbe controlled in various media. For example, self-propelled device 214can be configured for movement in media such as on flat surfaces, sandysurfaces or rocky surfaces.

The self-propelled device 214 may be implemented in various forms. Asdescribed below and with an embodiment of FIG. 3, the self-propelleddevice 214 may correspond to a spherical object that can roll and/orperform other movements such as spinning. In variations, device 214 cancorrespond to a radio-controlled aircraft, such as an airplane,helicopter, hovercraft or balloon. In other variations, device 214 cancorrespond to a radio controlled watercraft, such as a boat orsubmarine. Numerous other variations may also be implemented, such asthose in which the device 214 is a robot.

In one embodiment, device 214 includes a sealed hollow envelope, roughlyspherical in shape, capable of directional movement by action ofactuators inside the enclosing envelope.

Continuing to refer to FIG. 2A, device 214 is configured to communicatewith computing device 208 using network communication links 210 and 212.Link 210 transfers data from device 208 to device 214. Link 212transfers data from device 214 to device 208. Links 210 and 212 areshown as separate unidirectional links for illustration; in someembodiments a single bi-directional communication link performscommunication in both directions. It should be appreciated that link 210and link 212 are not necessarily identical in type, bandwidth orcapability. For example, communication link 210 from computing device208 to self-propelled device 214 is often capable of a highercommunication rate and bandwidth compared to link 212. In somesituations, only one link 210 or 212 is established. In such anembodiment, communication is unidirectional.

The computing device 208 can correspond to any device comprising atleast a processor and communication capability suitable for establishingat least uni-directional communications with self-propelled device 214.Examples of such devices include, without limitation: mobile computingdevices (e.g., multifunctional messaging/voice communication devicessuch as smart phones), tablet computers, portable communication devicesand personal computers. In one embodiment, device 208 is an IPHONEavailable from APPLE COMPUTER, INC. of Cupertino, Calif. In anotherembodiment, device 208 is an IPAD tablet computer, also from APPLECOMPUTER. In another embodiment, device 208 is any of the handheldcomputing and communication appliances executing the ANDROID operatingsystem from GOOGLE, INC.

In another embodiment, device 208 is a personal computer, in either alaptop or desktop configuration. For example, device 208 is amufti-purpose computing platform running the MICROSOFT WINDOWS operatingsystem, or the LINUX operating system, or the APPLE OS/X operatingsystem, configured with an appropriate application program tocommunicate with self-propelled device 214.

In variations, the computing device 208 can be a specialized device,dedicated for enabling the user 202 to control and interact with theself-propelled device 214.

In one embodiment, multiple types of computing device 208 can be usedinterchangeably to communicate with the self-propelled device 214. Inone embodiment, self-propelled device 214 is capable of communicatingand/or being controlled by multiple devices (e.g., concurrently or oneat a time). For example, device 214 can link with an IPHONE in onesession and with an ANDROID device in a later session, withoutmodification of device 214.

According to embodiments, the user 202 can interact with theself-propelled device 214 via the computing device 208, in order tocontrol the self-propelled device and/or to receive feedback orinteraction on the computing device 208 from the self-propelled device214. According to embodiments, the user 202 is enabled to specify input204 through various mechanisms that are provided with the computingdevice 208. Examples of such inputs include text entry, voice command,touching a sensing surface or screen, physical manipulations, gestures,taps, shaking and combinations of the above.

The user 202 may interact with the computing device 208 in order toreceive feedback 206. The feedback 206 may be generated on the computingdevice 208 in response to user input. As an alternative or addition, thefeedback 206 may also be based on data communicated from theself-propelled device 214 to the computing device 208, regarding, forexample, the self-propelled device's position or state. Withoutlimitation, examples of feedback 206 include text display, graphicaldisplay, sound, music, tonal patterns, modulation of color or intensityof light, haptic, vibrational or tactile stimulation. The feedback 206may be combined with input that is generated on the computing device208. For example, the computing device 208 may output content that ismodified to reflect position or state information communicated from theself-propelled device 214.

In some embodiments, the computing device 208 and/or the self-propelleddevice 214 are configured such that user input 204 and feedback 206maximize usability and accessibility for a user 202, who has limitedsensing, thinking, perception, motor or other abilities. This allowsusers with handicaps or special needs to operate system 200 asdescribed.

It should be appreciated that the configuration illustrated in theembodiment of FIG. 2A is only one of an almost unlimited number ofpossible configurations of networks including a self-propelled devicewith communication connections. Furthermore, while numerous embodimentsdescribed herein provide for a user to operate or otherwise directlyinterface with the computing device in order to control and/or interactwith a self-propelled device, variations to embodiments describedencompass enabling the user to directly control or interact with theself-propelled device 214 without use of an intermediary device such ascomputing device 208.

FIG. 2B depicts a system 218 comprising computing devices andself-propelled devices, according to another embodiment. In the exampleprovided by FIG. 2B, system 218 includes two computing devices 220 and228, four self-propelled devices 224, 232, 236, and 238, andcommunication links 222, 226, 230, 234 and 239. The communication ofcomputing device 220 with self-propelled device 224 using link 222 issimilar to the embodiment depicted in network 200 of FIG. 2A; however,embodiments such as those shown enable additional communication to beestablished between two computing devices 220 and 228, via network link226.

According to an embodiment such as provided with system 218, thecomputing devices 220, 228 may optionally control more than oneself-propelled device. Furthermore, each self-propelled device 224, 232,236, 238 may be controlled by more than one computing device 220, 228.For example, embodiments provide that computing device 228 can establishmultiple communications links, including with self-propelled devices 232and 236, and computing device 220.

In variations, the computing devices 220, 228 can also communicate withone or more self-propelled devices using a network such as the Internet,or a local wireless network (e.g., a home network). For example, thecomputing device 228 is shown to have a communications link 239, whichcan connect the computing device to an Internet server, a web site, orto another computing device at a remote location. In some embodiments,the computing device 228 can serve as an intermediary between thenetwork source and a self-propelled device. For example, the computingdevice 228 may access programming from the Internet and communicate thatprogramming to one of the self-propelled devices.

As an alternative or variation, the computing device 228 can enable anetwork user to control the computing device 228 in controlling one ormore of the self-propelled devices 232, 236, etc. Still further, thecomputing device 228 can access the network source in order to receiveprogrammatically triggered commands, such as a command initiated from anetwork service that causes one or more of the self-propelled devices toupdate or synchronize using the computing device 228. For example, theself-propelled device 232 may include image capturing resources, and anetwork source may trigger the computing device 228 to access the imagesfrom the self-propelled device, and/or to communicate those images tothe network source over the Internet.

In variations, such remote network functionality may alternatively becommunicated directly from a network source to the self-propelleddevices 224, 232, 236. Thus, computing devices 220, 228 may be optionaland various applications and uses. Alternatively, computing devices 220,228 may be separated from the self-propelled devices 224, 232, 236 by anetwork such as the Internet. Thus, computing devices 220, 228 canalternatively be the network source that remotely controls and/orcommunicates with the self-propelled devices.

It should be noted that the data communication links 210, 212, 222, 226,230, 234, 239, 242, 246, 248, and 252 in FIGS. 2A, 2B, and 2C aredepicted as short and direct for purposes of illustration. However,actual links may be much more varied and complex. For example, link 226connecting two computing devices 220 and 228 may be a low-power wirelesslink, if devices 220 and 228 are in close proximity. However, computingdevices 220 and 228 may be far apart (e.g., separated by miles orgeography), so long as suitable network communication can beestablished.

Thus, link 226 and all of the links 222, 230, 234, and 239 can employ avariety of network technologies, including the Internet, World Wide Web,wireless links, wireless radio-frequency communications utilizingnetwork protocol, optical links, or any available network communicationtechnology. The final connection to self-propelled devices 224, 232, 236and 238 is preferably wireless so connecting wires do not restrictmobility.

In one embodiment, the communication links 222, 226, 230 and 234 arebased on the wireless communication standard for data exchange known asBLUETOOTH. BLUETOOTH is widely available and provides a flexiblecommunication framework for establishing data networks usingshort-wavelength radio transceivers and data encoding. BLUETOOTHincorporates security features to protect the data sent on the linksfrom unauthorized observers or interference. Alternative wirelesscommunication medium may also be employed, such as wireless USB, Wi-Fi,or proprietary wireless communications. Embodiments further contemplatethat one or more of the communication links to 222, 226, 230 and 234utilize short-range radiofrequency (RF) communication, and/orline-of-sight communications.

In various other embodiments, the communication links are based on otherwireless communication systems. Various radio frequency datacommunication systems are available, including for example those knownas WI-FI, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g or 802.11n. Otherradio frequency data links are formed using cellular telephone serviceor serial communication protocols using radio modems. In otherembodiments, optical communication links are employed, includingmodulating properties of light and LASER beams.

Any suitable communication technology can be used to form the networklinks, whether presently known or available in the future. The featuresdescribed herein are not dependent on any particular networkingtechnology or standard.

In some embodiments, the communication established amongst the devices,such as amongst computing device 220, 228 and/or self-propelled devices224, 232, 236, can be temporary, flexible and reconfigurable. Aresulting network of such devices can be considered an “ad-hoc” network,or alternatively a “piconet,” or “personal area network.” In thisrespect, some implementations provide that the computing device is 220,228 and self-propelled devices 224, 232, 236 can be considered nodes ofthe network, such as an ad-hoc network. In such configurations, networkcomponents, topology and communications paths are flexible and can bereadily adjusted to accommodate addition or removal of devices, changingcommunication requirements or channel interference. For example,self-propelled device 238 in FIG. 2B is shown with no present networkconnection. However, self-propelled device 238 has connected to network218 in the past and received instructions to enable it to operatewithout a persistent network link.

FIG. 2C is a schematic that illustrates a system 268 comprising acomputing device and multiple self-propelled devices, under anotherembodiment. A computing device 240 is operable to communicate with oneor more self-propelled devices 244, 250, 254. The computing device 240may communicate commands or other control data, and received feedbacksimilar to embodiments described above. The self-propelled devices 244,250, 254 are configured to communicate and/or be controlled by thecomputing device 240. Additionally, the self-propelled devices 244, 250,254 are configured to communicate and/or control one another.

In the example shown by FIG. 2C, the computing device 240 communicateswith self-propelled device 244 using communications link 242.Self-propelled device 244 communicates with self-propelled device 250using link 246 and with self-propelled device 254 using link 248.Self-propelled devices 250 and 254 communicate using link 252. Thecomputing device 250 can send data to any of the self-propelled devices244, 250, or 254, using device 244 as a relay. Alternatively, thecomputing device 240 can communicate with the other self-propelleddevices 250, 254 directly.

The system 238 may include various configurations. For example, a usermay operate computing device 240 to control self-propelled device 244.Movement of the self-propelled device 244 may be communicated both tothe computing device 240 and to one or more of the other self-propelleddevices 250, 254. Each of self-propelled devices may be preprogrammed toreact in a specific manner based on state or position informationcommunicated from another one of the self-propelled devices. Forexample, self-propelled devices 244, 250 may each be operated in a repelmode, so that the movement of self-propelled device 244 (as controlledfrom computing device 240) results in a repel motion by theself-propelled device 250. In other variations, self-propelled devices244, 250, 254 may be preprogrammed to maintain a specific distance apartfrom one another, so that movement by one device automatically causesmovement by the other two devices. Still further, the devices 244, 250,254 may be configured so as to perform a variety of activities, such as,for example, (i) one self-propelled device automatically moving whenanother approaches a threshold distance; (ii) one self-propelled deviceprogrammatically moving to bump another self-propelled device; (iii) theself-propelled devices automatically moving in tandem based on inputreceived by each of the self-propelled devices from the otherself-propelled devices or from the computing device 240, and/orvariations thereof.

The various systems 200, 218, 238 are illustrative of embodimentsprovided herein. With any of the systems described, variations includethe addition of more or fewer computing devices, and/or more or fewerself-propelled devices. As described with some variations, additionalsources or nodes can be provided from a remote network source.Additionally, in some operational environments, the presence of thecomputing device is optional. For example, the self-propelled devicescan be partially or completely autonomous, using programming logic tofunction.

Spherical Mechanical Design

FIG. 3 is a block diagram illustrating the components of aself-propelled device 300 that is in the form of a robotic, sphericalball, in accordance with an embodiment. In one embodiment, robotic ball300 is of a size and weight allowing it to be easily grasped, lifted,and carried in an adult human hand.

As shown, robotic ball 300 includes an outer spherical shell (orhousing) 302 that makes contact with an external surface as the devicerolls. In addition, robotic ball 300 includes an inner surface 304 ofthe outer shell 302. Additionally robotic ball 300 includes severalmechanical and electronic components enclosed by outer shell 302 andinner surface 304 (collectively known as the envelope).

In the described embodiment, outer shell 302 and inner surface 304 arecomposed of a material that transmits signals used for wirelesscommunication, yet are impervious to moisture and dirt. The envelopematerial can be durable, washable, and/or shatter resistant. Theenvelope may also be structured to enable transmission of light and istextured to diffuse the light.

In one embodiment, the housing is made of sealed polycarbonate plastic.In one embodiment, at least one of the outer shell 302 or inner surface304 are textured to diffuse light. In one embodiment, the envelopecomprises two hemispherical shells with an associated attachmentmechanism, such that the envelope can be opened to allow access to theinternal electronic and mechanical components.

Several electronic and mechanical components are located inside theenvelope for enabling processing, wireless communication, propulsion andother functions (collectively referred to as the “interior mechanism”).Among the components, embodiments include a drive system 301 to enablethe device to propel itself. The drive system 301 can be coupled toprocessing resources and other control mechanisms, as described withother embodiments. Referring again to FIG. 3, carrier 314 serves as theattachment point and support for components of the interior mechanism.The components of the interior mechanism are not rigidly attached to theenvelope. Instead, the interior mechanism is in frictional contact withinner surface 304 at selected points, and is movable within the envelopeby the action of actuators of the drive mechanism.

Carrier 314 is in mechanical and electrical contact with energy storage316. Energy storage 316 provides a reservoir of energy to power thedevice and electronics and is replenished through inductive charge port326. Energy storage 316, in one embodiment, is a rechargeable battery.In one embodiment, the battery is composed of ithium-polymer cells. Inother embodiments, other rechargeable battery chemistries are used.

Carrier 314 can provide the mounting location for most of the internalcomponents, including printed circuit boards for electronic assemblies,sensor arrays, antennas, and connectors, as well as providing amechanical attachment point for internal components.

In one embodiment, the drive system 301 includes motors 322, 324 andwheels 318, 320. Motors 322 and 324 connect to wheels 318 and 320,respectively, each through an associated shaft, axle, and gear drive(not shown). The perimeter of wheels 318 and 320 are two points wherethe interior mechanism is in mechanical contact with inner surface 304.The points where wheels 318 and 320 contact inner surface 304 are anessential part of the drive mechanism of the ball, and so are preferablycoated with a material to increase friction and reduce slippage. Forexample, wheels 318 and 320 are covered with silicone rubber tires.

In some embodiments, a biasing mechanism is provided to actively forcethe wheels 318, 320 against the inner surface 304. In an exampleprovided, the spring 312 and end 310 can comprise a biasing mechanism.More specifically, spring 312 and spring end 310 are positioned tocontact inner surface 304 at a point diametrically opposed to wheels 318and 320. Spring 312 and end 310 provide additional contact force toreduce slippage of the wheels 318 and 320, particularly in situationswhere the interior mechanism is not positioned with the wheels at thebottom and where gravity does not provide adequate force to prevent thedrive wheels from slipping. Spring 312 is selected to provide a smallforce pushing wheels 318 and 320, and spring end 310 evenly againstinner surface 304.

Spring end 310 is designed to provide near-frictionless contact withinner surface 304. In one embodiment, end 310 comprises a roundedsurface configured to mirror a low-friction contact region at allcontact points with the inner surface 304. Additional means of providingnear-frictionless contact may be provided. In another implementation,the rounded surface may include one or more bearings to further reducefriction at the contact point where end 310 moves along inner surface304.

Spring 312 and end 310 are preferably made of a non-magnetic material toavoid interference with sensitive magnetic sensors.

Control Overview

FIGS. 4A, 4B and 4C illustrate a technique for causing controlledmovement of a spherical self-propelled device 402, in accordance withone or more embodiments. In FIG. 4A, self-propelled device is at rest ina stable orientation. With an X-, Y-, Z-axes frame of reference, thecenter of mass 406 (or center of gravity) of the device is aligneddirectly below (Z axis) the center of rotation 408, causing the deviceto be at rest. Reference mark 404 is included in the drawing toillustrate movement (X, Y axes), but is not present on the actualself-propelled device 402.

To produce directed movement of self-propelled device 402, the center ofmass 406 is displaced from under the center of rotation 408, as shown inFIG. 4B. With movement, the device 402 has an inherent dynamicinstability (DIS) in one or more axes (e.g., see Y or Z axes). Tomaintain stability, the device uses feedback about its motion tocompensate for the instability. Sensor input, such as provided fromsensors 112 (see FIG. 1) or accelerometers or gyroscopes (see FIG. 6),can be used to detect what compensation is needed. In this way, thedevice maintains a state of dynamic inherent instability as it movesunder control of sensors and control input, which can be communicatedfrom another controller device.

The displacement 410 of center of mass 406 is caused by one or moreactuators. When center of mass 406 is not aligned below center ofrotation 408, a torque is created on device 402 about the center ofrotation, causing device 402 to rotate to restore stability. When device402 is in contact with a surface, rotation causes device 402 to movealong the surface in the direction corresponding to the displacement410.

FIG. 4C illustrates device 402 at rest after the movement, withreference mark 404 showing the distance device 402 has rotated from theinitial position in FIG. 4A. Although the displacement of center of mass406 and movement are shown in one dimension for illustration, theprinciple applies to create desired motion in any direction on atwo-dimensional plane.

In some implementations, device 402 is configured with center of mass406 being as near to the inner surface of the sphere as possible, orequivalently to arrange components so that center of mass 406 is as lowas possible when the device is in a stable situation as shown in FIG.4A.

FIG. 5 further illustrates a technique for causing motion of aself-propelled spherical device, according to an embodiment. In the FIG.5, device 500 is shown, having center of rotation 502 and center of mass506, and in contact with planar surface 512. The drive mechanism forrobotic device 500 comprises two independently-controlled wheeledactuators 508 in contact with the inner surface of the enclosingspherical envelope of device 500. Also shown is sensor platform 504.Several components of device 500 are not shown in FIG. 5 for simplicityof illustration.

When it is desired that device 500 move at a constant velocity, thetechnique illustrated in FIGS. 4A, 4B and 4C can be extended as shown inFIG. 5. To achieve continuous motion at a constant velocity, thedisplacement of center of mass 506 relative to center of rotation 502 ismaintained by action of wheeled actuators 508. The displacement of thecenter of mass 506 relative to center of rotation 502 is difficult tomeasure, thus it is difficult to obtain feedback for a closed-loopcontroller to maintain constant velocity. However, the displacement isproportional to the angle 510 between sensor platform 504 and surface512. The angle 510 can be sensed or estimated from a variety of sensorinputs, as described herein. Therefore, in one embodiment, the speedcontroller for robotic device 500 can be implemented to use angle 510 toregulate speed for wheeled actuators 508 causing device 500 to move at aconstant speed across surface 512. The speed controller determines thedesired angle 510 to produce the desired speed, and the desired anglesetpoint is provided as an input to a closed loop controller regulatingthe drive mechanism.

FIG. 5 illustrates use of angle measurement for speed control; howeverthe technique can be extended to provide control of turns and rotations,with feedback of appropriate sensed angles and angular rates.

It can be seen from the foregoing discussion that knowledge of theorientation angles is useful, in various embodiments, for control of aself-propelled device. Measuring the orientation of the device is alsouseful for navigation and alignment with other devices.

FIG. 6 is a block diagram depicting a sensor array and data flowaccording to an embodiment. In FIG. 6, sensor array 612 provides a setof sensors for providing information to the self-propelled device,including for example, its position, orientation, rates of translation,rotation and acceleration. Many other sensors can be included to meetrequirements in various embodiments.

In one embodiment, sensor array 612 includes a 3-axis gyroscope sensor602, a 3-axis accelerometer sensor 604, and a 3-axis magnetometer sensor606. In one embodiment a receiver for the Global Positioning System(GPS) is included. However, GPS signals are typically unavailableindoors, so the GPS receiver is often omitted.

Due to limitations in size and cost, sensors in sensor array 612 aretypically miniaturized devices employing micro-electro-mechanical (MEMS)technology. The data from these sensors requires filtering andprocessing to produce accurate state estimates 616. Various algorithmsare employed in sensor fusion and state estimator 614. These algorithmsare executed by the processor on the self-propelled device.

Those familiar with the art will understand that the signals from sensorin sensor array 612 are imperfect and distorted by noise, interferenceand the limited capability of inexpensive sensors. However, the sensorsalso provide redundant information, so that application of a suitablesensor fusion and state estimator process 614 provides an adequate stateestimation 616 of the true state of the self-propelled device.

For example, in many situations, magnetometer data is distorted by straymagnetic fields and ferrous metals in the vicinity. Sensor fusion andstate estimator 614 are configured to reject bad or suspect magnetometerdata and rely on the remaining sensors in estimating the state 616 ofthe self-propelled device. In some embodiments, particular movements ofthe self-propelled device can be used to improve sensor data for desiredpurposes. For example, it can be useful to rotate self-propelled devicethrough an entire 360 degree heading sweep while monitoring magnetometerdata, to map local magnetic fields. Since the fields are usuallyrelatively invariant over a short period of time, the local fieldmeasurement is repeatable and therefore useful, even if distorted.

Architecture

FIG. 7 illustrates a system including a self-propelled device, and acontroller computing device that controls and interacts with theself-propelled device, according to one or more embodiments. In anembodiment, a self-propelled device 710 may be constructed usinghardware resources such as described with an embodiment of FIG. 1. Inone implementation, self-propelled device 710 is a spherical object suchas described with an embodiment of FIG. 3. A computing device 750 can bea multifunctional device, such as a mobile computing device (e.g., smartphone), tablet or personal computer in device. Alternatively, computingdevice 750 can correspond to a specialized device that is dedicated tocontrolling and communicating with the self-propelled device 710.

In an embodiment, self-propelled device 710 is configured to execute oneor more programs 716 stored in a program library 720. Each program 716in the program library 720 can include instructions or rules foroperating the device, including instructions for how the device is torespond to specific conditions, how the device is to respond to controlinput 713 (e.g., user input entered on the computing device 720), and/orthe mode of operation that the device is to implement (e.g., controlledmode, versus autonomous, etc.).

The program library 720 may also maintain an instruction set that isshared by multiple programs, including instructions that enable someuser input to be interpreted in a common manner. An application programinterface (API) 730 can be implemented on the device 710 to enableprograms to access a library of functions and resources of the device.For example, the API 730 may include functions that can be used withprograms to implement motor control (e.g., speed or direction), statetransition, sensor device interpretation and/or wireless communications.

In one implementation, the device 710 receives programs and programminginstructions wirelessly through use of the wireless communication port712. In variations, the device 710 receives programs and programminginstructions 782 from external sources 780 via other ports, such asexpansion port 120 (see FIG. 1). The programming resources may originatefrom, for example, a media provided to the user of the device (e.g., SDcard), a network resource or website where programs can be downloaded,and/or programs and/or instruction sets communicated via the wirelesscommunication port 712 from the computing device 750. In oneimplementation, the computing device 750 can be programmaticallyconfigured to interact and/or control the self-propelled device 710 withsoftware. Once configured, the computing device 750 communicatesinstructions coinciding with its programmatic configuration to theself-propelled device 710. For example, the computing device 750 maydownload an application for controlling or interacting with theself-propelled device 710. The application can be downloaded from, forexample, a network (e.g., from an App Store), or from a website, usingwireless communication capabilities inherent in the computing device 750(e.g., cellular capabilities, Wi-Fi capabilities, etc.). The applicationthat is downloaded by the computing device 750 may include aninstruction set that can be communicated to the self-propelled device710.

In an embodiment, the computing device 750 executes a program 756 thatis specialized or otherwise specific to communicating or interactingwith, and/or controlling the self-propelled device 710. In someembodiments, the program 756 that executes on the computing device 750includes a counterpart program 716A that can execute on theself-propelled device 710. The programs 756, 716A can execute as ashared platform or system. For example, as described below, the program756 operating on the computing device 750 may cooperate with thecounterpart runtime program 716A to generate input for theself-propelled device 710, and to generate output on the computingdevice 750 based on a data signal from the self-propelled device 710. Inan embodiment, the program 756 generates a user interface 760 that (i)prompts or provides guidance for the user to provide input that isinterpretable on the self-propelled device 710 as a result of thecounterpart runtime program 716A, resulting in some expected outcomefrom the self-propelled device 710; (ii) receives feedback 718 from theself-propelled device 710 in a manner that affects the content that isoutput by the program 756 operating on the computing device 750. In thelatter case, for example, computer-generated content may be alteredbased on positioning or movement of the self-propelled device 710.

More specifically, on the computing device, the program 756 can providea user interface 760, including logic 762 for prompting and/orinterpreting user input on the computing device. Various forms of inputmay be entered on the computing device 750, including, for example, userinteraction with mechanical switches or buttons, touchscreen input,audio input, gesture input, or movements of the device in a particularmanner.

Accordingly, the program 756 can be configured to utilize an inherentapplication program interface on the computing device 750, to utilizethe various resources of the device to receive and process input. Manyexisting multifunctional or general purpose computing devices (e.g.,smart phones or tablets) are configured to detect various kinds ofinput, including touchscreen input (e.g., multitouch input gestureinput), optical input (e.g., camera image sensing input), audio inputand device movement input (e.g., shaking or moving the entire device).The user interface 760 may include logic 762 to prompt the user forspecific kinds of input (e.g., include visual markers where a usershould place fingers, instruct the user or provide the user with thevisual and/or audio prompt to move the device, etc.), and to interpretthe input into control information that is signaled to theself-propelled device.

In some embodiments or implementations, the input generated on thecomputing device 750 is interpreted as a command and then signaled tothe self-propelled device 710. In other embodiments or implementations,the input entered on the computing device 750 is interpreted as acommand by programmatic resources on the self-propelled device 710. Byinterpreting user input in the form of commands, embodiments provide forthe self-propelled device 710 to respond to user input in a manner thatis intelligent and configurable. For example, the self-propelled device710 may interpret user input that is otherwise directional in nature ina manner that is not directional. For example, a user may enter gestureinput corresponding to a direction, in order to have the self-propelleddevice 710 move in a manner that is different than the inherentdirection in the user input. For example, a user may enter a leftwardgesture, which the device may interpret (based on the runtime program716A) as a command to stop, spin, return home or alter illuminationoutput, etc.

The user interface 760 may also include output logic 764 forinterpreting data received from the self-propelled device 710. Asdescribed with other embodiments, the self-propelled device 710 maycommunicate information, such as state information and/or positioninformation (e.g., such as after when the device moves) to the computingdevice 750. In one implementation, the communication from theself-propelled device 710 to the computing device 750 is in response toa command interpreted from user input on the computing device 750. Inanother implementation, the communication from the self-propelled device710 may be in the form of continuous feedback generated as result of thedevice's continuous movement over a duration of time. As described withother implementations and embodiments, the output onto device 750 maycorrespond to a computing device having one of various possible formfactors. The program 756 may configure the interface to graphicallyprovide gaming context and/or different user-interface paradigms forcontrolling the self-propelled device 710. The program 756 may operateto directly affect the content generated in these implementations basedon movement, position or state of the self-propelled device 710.

In operation, the self-propelled device 710 implements the programmaticruntime 716A using one or more sets of program instructions stored inits program library 720. The program runtime 716A may correspond to, forexample, a program selected by the user, or one that is run by defaultor in response to some other condition or trigger. Among otherfunctionality, the program runtime 716A may execute a set ofprogram-specific instructions that utilizes device functions and/orresources in order to: (i) interpret control input from the computingdevice 750; (ii) control and/or state device movement based on theinterpretation of the input; and/or (iii) communicate information fromthe self-propelled device 710 to the computing device 750.

In an embodiment, the program runtime 716A implements drive controllogic 731, including sensor control logic 721 and input control logic723. The sensor control logic 721 interprets device sensor input 711 forcontrolling speed, direction or other movement of the self-propelleddevice's drive system or assembly (e.g., see FIG. 1, 3 or 8D). Thesensor input 711 may correspond to data such as provided from theaccelerometer(s), magnetometer(s) or gyroscope(s) of the self-propelleddevice 710. The sensor data can also include other information obtainedon a device regarding the device's movement, position, state oroperating conditions, including GPS data, temperature data, etc. Theprogram 716A may implement parameters, rules or instructions forinterpreting sensor input 711 as drive assembly control parameters 725.The input control logic 723 interprets control input 713 received fromthe computing device 750. In some implementations, the logic 723interprets the input as a command, in outputting drive assembly controlparameters 725 that are determined from the input 713. The input drivelogic 723 may also be program specific, so that the control input 713and/or its interpretation are specific to the runtime program 716A. Thedrive assembly control logic uses the parameters, as generated throughsensor/input control logic 721, 723 to implement drive assembly controls725.

In variations, the sensor/input control logic 721, 723 is used tocontrol other aspects of the self-propelled device 710. In embodiments,the sensor/input control logic 721, 723 may execute runtime program 716Ainstructions to generate a state output 727 that controls a state of thedevice in response to some condition, such as user input our deviceoperation condition (e.g., the device comes to stop). For example, anillumination output (e.g., LED display out), audio output, or deviceoperational status (e.g., mode of operation, power state) may beaffected by the state output 727.

Additionally, the run time program 716A generates an output interface726 for the self-propelled device program 756 running on the computingdevice 750. The output interface 726 may generate the data thatcomprises feedback 718. In some embodiments, the output interface 726generates data that is based on position, movement (e.g., velocity,rotation), state (e.g., state of output devices), and/or orientationinformation (e.g., position and orientation of the device relative tothe initial reference frame). The output interface 726 may also generatedata that, for example, identifies events that are relevant to theruntime program 716A. For example the output interface 726 may identifyevents such as the device being disrupted in its motion or otherwiseencountering a disruptive event. In some embodiments, output interface726 may also generate program specific output, based on, for example,instructions of the runtime program 716A. For example, run-time program716A may require a sensor reading that another program would notrequire. The output interface 726 may implement instructions forobtaining the sensor reading in connection with other operationsperformed through implementation of the runtime program 716A.

According to embodiments, self-propelled device 710 is operable inmultiple modes relative to computing device 750. In a controlled mode,self-propelled device 710 is controlled in its movement and/or state bycontrol input 713, via control signals 713 communicated from thecomputing device 750. In some implementations, the self-propelled device710 pairs with the computing device 750 in a manner that affectsoperations on the computing device as to control or feedback. In someembodiments, self-propelled device 710 is also operable in an autonomousmode, where control parameters 725 are generated programmatically on thedevice in response to, for example, sensor input 711 and without needfor control input 713. Still further, in variations, the self-propelleddevice 710 can act as a controller, either for the computing device 750or for another self-propelled device 710. For example, the device maymove to affect a state of the computing device 750. The device canoperate in multiple modes during one operating session. The mode ofoperation may be determined by the runtime program 716A.

As described by an embodiment of FIG. 7 and elsewhere in theapplication, the self-propelled device 710 can include a library ofinstruction sets for interpreting control input 713 from the computingdevice 750. For example, the self-propelled device can storeinstructions for multiple programs, and the instructions for at leastsome of the programs may include counterpart programs that execute onthe controller device 750. According to embodiments, the library that ismaintained on the self-propelled device is dynamic, in that theinstructions stored can be added, deleted or modified. For example, aprogram stored on the self-propelled device may be added, or anotherprogram may be modified.

When executed on the computing device 750, each program may includeinstructions to recognize a particular set of inputs, and differentprograms may recognize different inputs. For example, a golf program mayrecognize a swing motion on the computing device 750 as an input, whilethe same motion may be ignored by another program that is dedicated toproviding a virtual steering mechanism. When executed on theself-propelled device 710, each program may include instructions tointerpret or map the control input 713 associated with a particularrecognized input to a command and control parameter.

In embodiments, the self-propelled device is able to dynamicallyreconfigure its program library. For example, an embodiment providesthat a program can be modified (e.g., through instructions received bythe controller device) to process control input 713 that corresponds toa new recognized input. As another example, an embodiment provides thatthe self-propelled device is able to switch programs while theself-propelled device is in use. When programs are switched, a differentset of inputs may be recognized, and/or each input may be interpreteddifferently on the self-propelled device 710.

FIG. 8A illustrates a more detailed system architecture 800 for aself-propelled device and system, according to an embodiment. As hasbeen previously discussed herein, in various embodiments, theself-propelled device 800 comprises multiple hardware modules, includingwireless communication 802, memory 804, sensors 806, displays 808,actuators 810 and an expansion port 812. Each of these modules isinterfaced with a set of software known as device drivers or hardwareabstraction layer (HAL) 820. HAL 820 provides isolation between specifichardware and higher layers of the software architecture.

An operating system 822 provides for support of general hardware inputand output, scheduling tasks, and managing resources to perform tasks.The operating system 822 is also sometimes known as a “hypervisor” whichprovides for sharing of resources among tasks, for example, if twosoftware modules request control of the actuators simultaneously,operation policy established by hypervisor 822 resolves the contention.

ORBOTIX predefined local control functions 824 comprise control loopsand library routines useful to robot applications 825. In someembodiments, a set of local robot applications 825 controls some or allof the features of self-propelled device 800. In some embodiments, a setof predefined remote control functions 826 interfaces with a remotecontroller device such as a computing device, using wireless link 802.

In one embodiment, a Robot Application Programming Interface (API) 828provides a documented set of functions usable to control and monitor thedevice hardware and functions. API functions, also known as userfunctions 832, can be supplied by a user or obtained from a softwarerepository or website and downloaded to the self-propelled device. Userfunctions 832 are stored in user function storage 830.

In one embodiment, a robot language interpreter 834 is provided. Therobot language interpreter 834 processes program instructions written ina simple, easy to understand format. For example, in one embodiment,language interpreter 834 processes instructions written in a variant ofthe BASIC programming language with extensions for reading robot sensors806, controlling displays 808 and actuators 810, and interfacing withother robot device hardware and features. Robot language interpreter 834also provides protection and security against performing destructive orunwise operations. In one embodiment, language interpreter 834understands the ORBBASIC language from ORBOTIX. Robot language code 838is stored in dedicated robot language storage 836.

An example of user code 838, when executed by interpreter 834, causesthe self-propelled device's LED display to change color in response tothe measured speed of movement of the device. Thus it can be seen that auser-supplied function can control one element of the device, such asLED display, while other elements (speed and direction) remaincontrolled through the wireless connection and remote control device.

Thus, multiple methods are provided for a user to add programmaticinstructions to control and extend the features of the self-propelleddevice. API 828 provides a powerful interface for a sophisticated user,while language interpreter 834 provides a simple and safer interface fora novice that can also negate time lags in communication with acontroller device.

FIG. 8B illustrates the system architecture of a computing device 840,according to an embodiment. As previously described herein, computingdevices useful in networks with self-propelled devices typically providea wireless communication interface 841, a user interface 845, with otherhardware and features 846.

Device 840 typically provides an operating system 848, for example iOSfor an APPLE IPHONE and ANDROID OS for ANDROID computing devices. Alsoprovided is an API 850 for applications. ORBOTIX application base 852provides basic connectivity to device API 850 and device OS 848 withhigher layers of application software.

ORBOTIX controller application programs, or “apps” 854 and 858, provideuser experiences and interaction with self-propelled devices. Forexample, in various embodiments, apps 854 and 858 provide control of aself-propelled device using touch-sensing control or a simulatedjoystick controller. Apps 854 and 858 can also provide a solo ormulti-player game experience using self-propelled or robotic devices.

In some embodiments, controller apps 854 and 858 use sensors on device840 to allow gestural control of a physical device in a real worldenvironment, controlling a self-propelled or robotic device. Forexample, a user can make a gesture used in a sports game—a tennis swingor golf swing. The gesture is sensed on device 840 and processed by asoftware app to cause corresponding motion of the self-propelled device.

ORBOTIX API/SDK (Software Development Kit) 856 provides a documented setof interface functions useful to a user desiring to create customapplications 858 on a controller device for use with a self-propelledrobotic device.

App 854 differs from app 858 in that app 854 is built directly on theapplication base layer 852, while app 858 is built on ORBOTIX controllerAPI/SDK 856.

FIG. 8C illustrates a particular feature of code execution according toan embodiment. Shown are two computing devices 842 and 846. Device 842is not necessarily the same type as device 846. One device may be anIPHONE and one an ANDROID phone. Each device has an associated memorystorage area, memory 849 for device 846 and memory 844 for device 842.Robot code 847 is loaded into both memories 844 and 849, and issubsequently available to transfer to robot API 850.

A notable feature in this embodiment is that code module 847 is storedand transferred into robot API 850 using an intermediate computingdevice 842 or 846, and the type of the computing device does not matter.This makes it possible for computing devices to store various codemodules or “helper apps” that can be downloaded to robotic devices asneeded, for example to expedite a particular task.

It should be appreciated that the embodiments and features discussed inrelation to FIGS. 8A, 8B and 8C provide a highly flexible distributedprocessing platform, wherein tasks can be readily moved between acontroller and controlled device.

Control Systems

According to at least some embodiments, a self-propelled device such asdescribed by various examples herein moves in accordance with athree-dimensional reference frame (e.g., X-, Y- and Z-axes), butoperates using input that is received from a device that uses atwo-dimensional reference frame (e.g., X-, Y-axes). In an embodiment,the self-propelled device maintains an internal frame of reference aboutthe X-, Y- and Z-axes. The self-propelled device is able to receivecontrol input from another device, in which the control input is basedon a two-dimensional reference frame and further controls the movementof the self-propelled device about the X-, Y- and Z-axes.

FIG. 8D illustrates an embodiment in which a self-propelled device 800implements control using a three-dimensional reference frame and controlinput that is received from another device that utilizes atwo-dimensional reference frame, under an embodiment. The self-propelleddevice 800 (assumed to be spherical) includes a control system 882 thatincludes a three-axis controller 880 and an inertial measurement unit(IMU) 884. The IMU 884 uses sensor input to provide feedback that thecontroller 880 can use to independently determine a three-dimensionalframe of reference for controlling a drive system 890 (e.g., see FIG. 3)of the self-propelled device. Specifically, the three-axis controller880 operates to implement control on motors 892 (or wheels 894) of thedrive system 890. For example, the three-axis controller 880 operates todetermine the speeds at which each of two parallel wheeled motors 894,894 are to spin. It should be appreciated that the two motors 892, 892,which can be operated in varying degrees of cooperation and opposition,are capable of moving the sphere 800 in many rotational andtranslational motions to achieve a desired movement. In one embodiment,the motors 892, 892 are capable of rotating at varying speeds in bothforward and reverse directions to affect the movement of thecorresponding wheels 894, 894. In another embodiment, each motor 892,892 speed is varied from zero to a maximum in one direction.

The controller 880 and IMU 884 can be implemented through separatehardware and/or software. In one implementation, the controller 880 andIMU 884 are implemented as separate software components that areexecuted on, for example, processor 114 (see FIG. 1).

More specifically, the controller 880 measures or estimates the presentstate of the self-propelled device 800, including pitch, roll, and yawangles based on feedback 895. The feedback 895 may originate from, forexample, one or more accelerometers 896A, gyroscope 896B, magnetometer896C, and/or other devices (e.g., GPS), which determine the feedbackwhen the device is in motion.

In one embodiment, controller 880 receives feedback 895 from the IMU 884as to the motion of the device along three axes, including a desiredpitch input, a desired roll input and a desired yaw input. In onevariation, the feedback 895 includes desired orientation angles. Stillfurther, the feedback can correspond to desired rates of angularrotation.

In one embodiment, the desired pitch angle is calculated by anadditional control loop configured to maintain forward speed. Asdescribed in conjunction with FIG. 5, speed and pitch angle are relatedby the physics of a rolling sphere.

In addition to feedback 895, the controller uses control input 885 fromthe controller device to implement control on the drive system 890. Thecontrol input 885 may originate from a device that utilizes atwo-dimensional reference frame (e.g., X and Y). In one implementation,the control input 885 is determined by, for example, processingresources of the self-propelled device 800 that interpret control datafrom the controller 880 as commands that specify one or more parameters,such as parameters that specify position (e.g., move to a position),distance, velocity or direction. Thus, some embodiments provide that thecontrol input 885 is based on control data that is (i) generated inaccordance with a two-dimensional reference frame, and (ii) interpretedas one or more commands that specify parameters such as distance,position or velocity. For example, a desired speed is provided by way ofcontrol input 885 to the controller 880. In an embodiment, thecontroller 880 implements control 888 on the drive system 890 usingcontrol parameters 898, which account for the control input 885 and thefeedback 895. The control 888 may cause individual components of thedrive system 890 to compensate for instability, given, for example,parameters specified in the control input (e.g., command input). Inother words, the controller 880 may implement control 888 in a mannerthat causes the drive system 890 to adjust the motion of the devicebased on feedback 895, in order to effectively implement the controlparameters (e.g., distance to travel) specified in the command input.Furthermore, the control 888 enables the device to maintain control withpresence of dynamic instability when the device is in motion.

In some embodiments, the controller 880 is able to determine, fromfeedback 895, the present state of the self-propelled device 800 inconjunction with desired angles. As mentioned, the controller 880 canuse the feedback 895 to implement control parameters, particularly as tocompensating for the dynamic instability (see also FIG. 4B) that isinherent in about one or more axes when the self-propelled device is inmotion. The errors can be determined for each axis (e.g., pitch, rolland yaw). This uses a technique of feedback where the actual angle iscompared to the desired angle, in each axis, to calculate an error orcorrection signal.

According to embodiments, the controller 880 uses the feedback 895 toestablish multiple control loops. In one embodiment, the controller 880computes an estimated set of state variables, and uses the estimatedstate variables in a closed loop feedback control. This allows themultiple feedback control loops to be implemented, each of which controlor provide feedback as to a state, such as, for example, a position,rate, or angle. The controller 880 can implement feedback control usingestimated states, so as to provide for controlled movement of theself-propelled device, both along a surface and in device rotation aboutaxes. The controlled movement can be achieved while the device isinherently unstable during movement.

In addition, incorporating feedback input 895 using sensors andestimation of present state variables enables feedback control 898 fordevice stability in both static and dynamic conditions. It can beappreciated that actuators in embodiments of a self-propelled devicewill not respond consistently or cause identical command response, dueto disturbances such as variations in actuators, environment, noise andwear. These variations would make stable, controlled movement difficultwithout feedback control. Feedback control can also provide stabilityaugmentation to a device that can be inherently unstable and allowsmovement in a controlled and stable manner.

Now the controller has calculated three correction signals and thesignals must be combined into command signals to each of the two motors.For reference, the two motors are termed “left” and “right”, although itshould be understood the assignment of these terms is arbitrary. It canbe appreciated that the assignment of labels affects the signconventions in roll and yaw.

Then, the following equations are used to combine the correction termsinto left and right motor commands.

First, the pitch and yaw corrections are combined into intermediatevariables. In one embodiment, the pitch correction is limited to preventthe motors from being driven at full speed to create forward motion,which would prevent response to roll or yaw correction inputs.

-   -   left_motor_intermediate=pitch correction+yaw correction    -   right_motor_intermediate=pitch correction−yaw correction

Next, the roll correction is included appropriately into the left andright motor variables. If the roll correction is positive, rollcorrection is subtracted from the left motor command:

-   -   left_motor_output=left_motor_intermediate−roll_correction    -   right_motor_output=right_motor_intermediate.

Alternatively, if the roll correction is not positive, roll correctionis added to the right motor variable:

-   -   left_motor_output=left_motor_intermediate    -   right_motor_output=right_motor_intermediate+roll_correction

Thus the controller produces an output variable for each motor thatincludes the desired control in three axes.

In this way, a controller can use a two-dimensional reference frame toprovide input for the self-propelled device (which utilizes athree-dimensional reference frame). For example, the controller canimplement a graphic user interface to enable the user to input that isbased on two-dimensional input. For example, FIG. 11B illustrates agraphic control mechanism that can be implemented on a controller deviceto enable the user to provide directional input about the X and Y axes(see also FIG. 12A).

Methodology

FIG. 9 illustrates a method for operating a self-propelled device usinga computing device, according to one or more embodiments. Reference maybe made to numerals of embodiments described with other figures, andwith FIG. 7 in particular, for purpose of illustrating suitablecomponents or elements that can be used to perform a step or sub-stepbeing described.

According to an embodiment, when a session is initiated between theself-propelled device 710 and computing device 750 (e.g., self-propelleddevice is turned on and the self-propelled device program 756 islaunched on the computing device 750), the two devices calibrate theirrespective orientation (910). In one implementation, the self-propelleddevice 710 obtains its orientation and/or position relative to theinitial reference frame, then signals the information to the computingdevice 750.

In an embodiment in which the self-propelled device 710 is spherical(e.g., a ball), the self-propelled device 710 can base its orientationdetermination on the location of the device marker. The device markermay correspond to a predetermined feature on the device. The location ofthe feature relative to an initial reference frame is obtained andcommunicated to the computing device 750. The computing device 750 mayinclude a user-interface that includes an orientation that is based onthe orientation information communicated from the self-propelled device710. For example, the user interface 760 of computing device 750 maygenerate a graphic steering mechanism that is calibrated to reflect theorientation of the self-propelled device 710 (e.g., based on thepredetermined marker on the self-propelled device 710).

Control input is received on the self-propelled device from thecomputing device running the self-propelled device program 756 (920).The control input may be in the form of a command, or otherwise be inthe form of data that is interpretable on the self-propelled device 710(through use of programming). The control input may include multiplecomponents, including components from different input or interfacemechanisms of the computing device 750 (e.g., touchscreen andaccelerometer of the computing device 750). Accordingly, implementationsprovide for control input to be based on touchscreen input (922),mechanical switch or button inputs (924), device motion or positioninput (926), or combinations thereof (928). In variations, other formsof input can be entered on the computing device 750 and processed ascontrol input. For example, the computing device 750 may communicate tothe self-propelled device 710 one or more of (i) audio input from theuser speaking, (ii) image input from the user taking a picture, and/or(iii) GPS input.

In an embodiment, the control input is interpreted on the self-propelleddevice 710 using programming (930). Thus, the self-propelled device 710may receive different forms of input from the computing device 750,based on the program executed on the self-propelled device 710 and/orthe computing device 750. Moreover, self-propelled device 710 and/or thecomputing device 750 implement different processes for how input of agiven type is to be interpreted. For example, self-propelled device 710can interpret touchscreen inputs differently for different programs, andthe response of the self-propelled device may be determined by whichprogram is executing when the input is received.

In using programming to interpret input, self-propelled device 710 maybe capable of different forms of responses to input. Based on theprogram that is executed on the self-propelled device 710 and/or thecomputing device 750, the input of the user may be interpreted asdirectional input (932), non-directional input (934), and/or amulti-component command input (936). More specifically, the device maybe correlated to input that is directional in nature by interpretinguser actions or input data that includes an inherent directional aspect.For example, a user may operate a graphic steering wheel to control thedirection of the self-propelled device 710. The device may also processinput non-directionally. For example some forms of user input or actionmay have inherent directional characteristics (e.g., the user swingingcomputing device 750 in a particular direction, the user providing somedirectional input on the steering wheel mechanism that is graphicallydisplayed on the computing device, etc.), but the manner in which theinput is processed on the self-propelled device 710 may not bedirectional, or least directional in a manner that is similar to theinherent directional characteristic of the user action.

In variations, action performed by the user on the computing device 750may also be interpreted as a command. The input from the user on thecomputing device 750 may be correlated (either on the computing device750 or the self-propelled device 710) with instructions that signify anaction by the device. The correlation between input and action can beprogram-specific, and configurable to meet the requirements or objectsof the particular program that is being executed. As an example, theself-propelled device 710 can interpret a single user action (e.g.,gesture input on computing device) as a command to perform a series ofactions, such as actions to perform a combination of movement, statechanges, and/or data outputs.

The device performs one or more actions that are responsive to the useraction or actions (940). The response of the self-propelled device 710may be dictated by the program that is executing on the device (as wellas the computing device 750) when the control input is received. Thus,the action or actions performed by the self-propelled device 710 may becomplex, and multiple actions can be performed based on a single commandor series of user actions.

For example, the self-propelled device 710 and the computing device 750may combine to enable the user in simulating a game in which a ball(such as a tennis ball) is struck against the wall. To simulate thegame, the user may swing computing device 750 in a given direction(e.g., like a racquet), causing the self-propelled device 710 to move ina direction that is related to the direction of the user's motion.However, without further input from the user, the self-propelled device710 may return or move in a substantially opposite direction after theinitial movement, so as to simulate the ball striking a wall or anotherracquet and then returning. Thus, the return of the self-propelleddevice 710 would be non-directional in its relation to the inherentdirectional characteristic of the original action.

The same example also illustrates the use of command input, in that oneinput on the computing device 750 (user swinging device) is interpretedinto multiple actions that are taken by the self-propelled device 710.Moreover, based on programming, the self-propelled device 710 and/or thecomputing device 750 may interpret multiple kinds of user input oraction as a command, resulting in performance of one action, or a seriesof actions. For example, in the ball example described above, the usermay also be required to place his finger on the touchscreen of thecomputing device 750, while swinging the device in a particulardirection. The combination of the touchscreen input and the motion inputof the computing device 750 can be interpreted as a command for multipleactions to be performed by the self-propelled device 710. In the exampleprovided, the self-propelled device performs the following in responseto multi-component user action: determine a velocity and direction basedon the user action (e.g., user places finger and touchscreen whileswinging computing device 750); move based on the determined velocityand direction; determine when to stop based on the simulated presence ofa wall; estimate return velocity and direction; and then move in thereturn direction.

Additionally, each action or output from the self-propelled device 710may incorporate several independent sub actions, involving independentlyoperable aspects of the self-propelled device 710. For example,self-propelled device 710 may include multiple motors that comprise thedrive assembly. A command input may dictate whether one or both motorsare used. Likewise, command input may determine if other hardwareresources of the device are used in response to user input. For example,the command input can correlate a user input on the computing devicewith a series of actions on the self-propelled device 710, which includecommunicating an output of a magnetometer to the computing device 750.

Other types of command input that can be interpreted from a user actioninclude, for example, altering the state of the self-propelled device710 based on a particular input from the user. For example, the user mayperform a double tap on the touchscreen of the computing device 750 as aform of input. A first program on the self-propelled device 710 mayinterpret the double tap as a command to spin. A second program on thesame self-propelled device 710 may interpret the double tap as a commandto illuminate.

In some embodiments, the self-propelled device 710 signals backinformation (e.g., feedback 718) to the computing device 750 (950). Thefeedback 718 may correspond to the updated position information (952),information about the device's movement or orientation (e.g., velocityor direction), device state information (954), or other information(956) (e.g., sensor input from the device based on specific programmingrequest). As described with some embodiments, the feedback 718 may beused to generate content on the computing device 750. For example, thefeedback 718 may affect a virtual representation of the self-propelleddevice 710 generated on the computing device 750. With, for example,movement of the self-propelled device 710, the corresponding virtualrepresentation of the self-propelled device on the computing device 750may also be moved accordingly. Numerous examples are provided herein foruser feedback 718 to generate and/or alter content on the computingdevice 750.

FIG. 10 illustrates a method for operating a computing device incontrolling a self-propelled device, according to one or moreembodiments. Reference may be made to numerals of embodiments describedwith other figures for the purpose of illustrating suitable componentsor elements for performing a step or sub-step being described.

The computing device 750 may include a contextual user interface (1010).For example, the user interface generated on the computing device 750may include a graphic interface that provides features for implementingthe game or simulation. The features may include use of a graphic objectthat is virtually moved in accordance with movement of theself-propelled device 710. Specific examples of user interfaces include,for example: (i) a user interface having a circle, and an orientationmarker that the user can move about the circle, where the orientationmarker represents the orientation of the self-propelled device; (ii) agolfing or bowling interface showing a virtualized ball that representsthe self-propelled device; or (iii) a dynamic and interactive gamingcontent in which an object representing the self-propelled device 710 ismoved in the context of gaming or simulation content.

A user may operate the computing device 752 to enter one or more inputs(1020). The input may be either discrete (in time) or continuous.Discrete input may correspond to a specific user action that iscompleted, and results in the self-propelled device 710 moving and/orperforming other actions. Examples of discrete inputs include simulatedgolf swings or bowling strokes (e.g., where the user swings his handsetand the action is interpreted as a golf or bowling ball movement).Continuous input requires the user to be engaged while theself-propelled device moves. Examples of continuous input include theuser operating a virtual steering feature or joy stick as a mechanismfor controlling the self-propelled device in its movement. As mentionedwith some other embodiments, the user input may correspond to multipleactions performed by the user, including actions that include the use ofdifferent input interfaces or mechanisms on the computing device 750.For example, the user input can correspond to user actions on thetouchscreen display, the user moving the computing device about thegesture, the user interacting with the camera to the computing device,the user providing speech input from a microphone of the computingdevice, and/or the user operating buttons and/or mechanical switches onthe computing device.

The user input is communicated to the self-propelled device (1030). Inone embodiment, the computing device 750 interprets the input of theuser, and then signals interpreted input to the self-propelled device710. In variations, the self-propelled device 710 interprets the inputof the user, based on data signals received from the computing device750.

The self-propelled device 710 may respond to the user input, by, forexample, moving in a direction and/or in accordance with the velocityspecified by the user input (1040). Other actions, such as spinning,performing other movements, changing state of one or more devices, etc.can also be performed, depending on the interpretation of the userinput.

The computing device 750 may receive the feedback from theself-propelled device 710 (1050). The nature and occurrence of thefeedback may be based on the programmatic configuration of theself-propelled device 710 and the computing device 750. For example, thefeedback communicated from the self-propelled device 710 to thecomputing device 750 may include information that identifies position,orientation and velocity of the self-propelled device, either at aparticular instance or over a given duration of time. As an alternativeor addition, the feedback may include or state information about theself-propelled device 710, and/or readings from one or more sensors onthe self-propelled device. Furthermore, depending on the implementation,the feedback may be communicated either continuously or discretely. Inthe latter case, for example, the self-propelled device 710 may performan action, such as moving to a particular position, and then communicateits position and orientation to the computing device 750. Alternatively,the self-propelled device 710 may continuously update the computingdevice 750 on this orientation and/or position and/or velocity, as wellas state other information. Numerous variations are possible, dependingon the programmatic configuration of the self-propelled device 710.

In response to receiving the feedback, the computing device 750 updates,modifies or generates new contextual user interfaces that reflects achange in the representation of the self-propelled device (1060).Specifically, once the self-propelled device 710 moves, itsrepresentation of the user interface on the computing device 750 mayreflect the movement. For example, the contextual user interface of thecomputing device may reflect the movement of the self-propelled device710 in a manner that is not video (or at least not solely video), butrather computer-generated (e.g., animated, graphic, etc.). As anaddition or alternative, other information communicated with thefeedback (e.g., the state of the self-propelled device 710) may also bereflected in the user interface of the computing device 750. Forexample, if the self-propelled device 710 is illuminated, its virtualrepresentation of the user interface of the computing device 750 maychange to reflect that illumination.

FIG. 14A through FIG. 14C, discussed below, provide further examples andextensions of embodiments in which the self-propelled device isrepresented in a virtual context on the controller device.

User Control Orientation

FIG. 11A through FIG. 11C illustrate an embodiment in which a userinterface of a controller is oriented to adopt an orientation of aself-propelled device, according to one or more embodiments. Inembodiments shown, a self-propelled device 1102 maintains apre-determined reference frame that indicates, for example, a forwardfacing direction. With reference to FIG. 11A, the self-propelled device1102 is shown to be spherical, although other form factors may beadopted (including crafts or vehicles). As a spherical device, however,self-propelled device 1102 is relatively featureless and lacks structurethat would otherwise indicate to the observer what the device's frame ofreference is, such as what the forward-facing direction of the deviceis. In order to identify the frame of reference, the self-propelleddevice 1102 can optionally include an outwardly visible marker 1104 orsurface feature that identifies the frame of reference. For example, themarker 1104 can correspond to a light-emitting component thatilluminates to mark a forward-facing surface 1106 of the device. Thelight-emitting component can, for example, correspond to a lightemitting diode (LED) that resides with the exterior of the device, oralternatively, within the interior of the device so as to illuminate theforward-facing surface 1106 from within the (e.g., the exterior of thedevice may be translucent).

The device 1102 can maintain its own frame of reference, using resourcesthat reside on the device. For example, device 1102 may utilize sensorssuch as a magnetometer (determine north, south, east west), an IMU (seeFIG. 8D), a GPS, and/or stored position or state information in order todetermine its frame of reference.

FIG. 11B illustrates a controller device 1120 for controlling theself-propelled device 1102. The controller device 1120 includes adisplay screen 1121 on which a user-interface feature 1122 is providedto enable control of the self-propelled device 1102. The user-interfacefeature 1122 may enable the user to enter, for example, directionalinput in order to steer the self-propelled device 1102. According toembodiments, the orientation of the user-interface feature 1122 iscalibrated to match the orientation of the self-propelled device 1102,based on the frame of reference maintained on the self-propelled device1102. For example, the user-interface feature 1122 may include a marker1124 that serves as a point of contact for interaction with the user.The relative orientation of the marker 1124 on the user-interfacefeature 1122 may be set to match the orientation of the marker 1104 ofthe self-propelled device 1102. Thus, in the example provided, theforward-facing orientation of the self-propelled device 1102 may bedirected west, and the user may maintain the forward-direction bykeeping the marker 1124 in the west direction.

According to embodiments, the orientation of the self-propelled device1102 with respect to the device's internal frame of reference dictatesthe orientation of the user-interface 1122 (e.g., the direction of themarker 1124). For example, FIG. 11C can serve as an illustration of thecontroller 1120 being rotated (e.g., the user moves the controller whileholding it) relative to the self-propelled device 1102. The marker 1124of the user-interface 1122 may be set to the orientation of the marker1104 on the self-propelled device 1102, so that, for example, the westdirection remains forward-facing.

FIG. 11D illustrates a method for calibrating a user-interface fororientation based on an orientation of the self-propelled device,according to an embodiment. While reference is made to elements of FIG.11A through FIG. 11C for purpose of illustrating suitable elements orcomponents for performing a step or sub-step being described, anembodiment such as described by FIG. 11D may be readily employed withother forms of devices.

The self-propelled device 1102 operates to determine its orientation,relative to an internal frame of reference that is determined fromresources of the device (1150). The self-propelled device 1102 candetermine its orientation in response to events such as theself-propelled device 1102 (i) being switched on, (ii) being connectedwirelessly to the controller device 1120, (iii) after a set duration oftime, (iv) after user input or command, and/or (v) after a designatedevent, such as a bump that makes the device “lost”.

The self-propelled device 1102 signals information to the controller1120 that indicates the orientation of the self-propelled device 1102relative to the device's frame of reference (1160). The information maybe signaled wirelessly through, for example, BLUETOOTH or other forms ofwireless communication mediums.

The controller 1120 may initiate a program or application to control theself-propelled device 1102 (1170). For example, a control program may beoperated that initiates the controller 1120 in connecting with theself-propelled device 1102. The program may generate a user-interface1122 that displays content in the form of a virtual controller for theself-propelled device 1102. The virtual controller can include a markeror orientation that indicates front/back as well as left/right.

Based on the information received from the self-propelled device 1102,the controller 1120 configures the user-interface 1122 so that themarker or orientation is aligned or otherwise calibrated with theorientation maintained on the device (1180). For example, as a result ofthe calibration or alignment, both the self-propelled device 1102 andthe controller 1120 recognize the frontal direction to be in the samedirection (e.g. north or west).

Numerous variations may be provided to the examples provided. Forexample, the user-interface 1122 can include alternative steeringmechanisms, such as a steering wheel or virtual joystick (see also FIG.12A). The manner in which the user-interface 1122 can be configured toprovide directional input can also be varied, depending on, for example,the virtual model employed with the user-interface (e.g., steering wheelor joystick).

Controller Interface and Usage Scenarios

FIG. 12A and FIG. 12B illustrate different interfaces that can beimplemented on a controller computing device. In FIG. 12A, contentcorresponding to a steering mechanism is illustrated to control thevelocity and direction of a self-propelled device. In FIG. 12B, contentcorresponding to a gaming interface (e.g., golf) is depicted that showsa representation of the self-propelled device in the form of a golfball. The user can interact with the devices shown (e.g., take golfswing with the controller/computing device) to direct the self-propelleddevice to move. In turn, the content generated on the computing devicecan be reconfigured or altered. In particular, the representation of theself-propelled device can be affected. For example, the golf ball may bedepicted as moving when the self-propelled device moves.

FIG. 13A through FIG. 13C illustrate a variety of inputs that can beentered on a controller computing device to operate a self-propelleddevice, according to an embodiment. In FIG. 13A and FIG. 13B, the usercan be prompted by graphic features 1302 to place fingers on a givenarea of a display screen 1304. For example, two finger positioning canbe used for a golf example, and three finger positioning can be used fora bowling example. With fingers placed, the device 1300 can be moved inan arc motion to simulate a golf stroke or bowler arm motion (FIG. 13C).The examples illustrate cases in which multiple types of input arecombined and interpreted as a set of commands with one or moreparameters (e.g., parameters dictating direction and velocity orposition of the self-propelled device). For example, a guided touchscreen input (first type of input) performed concurrently with movementof the controller device (second type of input) in an arc fashion can beinterpreted as a command to move the self-propelled device in a givendirection for a designated distance (e.g., for golfing or bowlingexamples).

Virtual Object Representation and Interaction

Some embodiments enable the self-propelled device to be virtuallyrepresented on an interface of the controller device. In suchembodiments, the degree to which the self-propelled device and itsvirtual representation are linked may vary, depending on desiredfunctionality and design parameters. For example, in gamingapplications, some events that occur to the self-propelled device (e.g.,bumps) may be conveyed and represented (e.g., virtual bump) with thedevice representation.

With reference to FIG. 14A, the self-propelled device 1400 may beoperated in a real-world environment, and virtually represented by agraphic object 1412 that is part of the user-interface of the controllerdevice 1402. The implementation may be provided by executing acorresponding program or instruction set on each of the self-propelleddevice 1400 and controller device 1402 (e.g., a game). Based on theimplemented instruction set, a relationship can be established betweenthe self-propelled device 1400 and the virtual representation 1412. Therelationship can be established by way of the self-propelled device 1400signaling state information 1405 to the controller device 1402, and thecontroller device signaling control information 1415 based on user-inputand virtual events.

As described with other embodiments, the self-propelled device 1400 mayoperate in a three-dimensional reference frame and the controller device1402 may operate in a two-dimensional reference frame. Theself-propelled device 1400 can include a three-dimensional controllerthat processes two-dimensional control information 1415 (e.g., userinput and virtual events) in its three-dimensional reference frame. Thethree-dimensional environment of the self-propelled device 1400 may berepresented two-dimensionally on the controller device 1402.

Examples of the relationships can include: (i) the self-propelled device1400 communicates its state (e.g., position information) to thecontroller device 1402, which reflects a corresponding change in theposition of the virtual object 1412—for example, both the self-propelleddevice and the controller device 1402 may trace a similarly shaped path;(ii) the user can enter input that moves or changes position of thevirtual representation 1412, and this change is reflected by real-worldmovement of the self-propelled device 1400; (iii) an event that occursto the self-propelled device 1400 is conveyed and/or represented in thevirtual environment of the virtual representation 1412—for example, theself-propelled device may collide with an object, causing lateralmovement or stoppage, and this event may be communicated virtually withthe object 1412 being bumped, stopped or even made to change color toreflect the event; and (iv) an event that occurs to the virtualenvironment of the virtual representation 1412 is conveyed to theself-propelled device—for example, a virtual collision between thevirtual representation 1412 and another virtual object (e.g., wall,zombie, etc. in gaming environment) may result in the movement of thevirtual object 1412 being changed, and this change may be communicatedas control input to the self-propelled device 1402 which can shake, stopor move unexpectedly to simulate the virtual collision). Numerousvariations may be implemented with respect to the manner in which theself-propelled device is linked to a virtual environment.

FIG. 14B and FIG. 14C illustrate an application in which aself-propelled device acts as a fiducial marker, according to anembodiment. In the example shown, a gaming environment is provided inwhich the user can steer the self-propelled device through, for example,tilting or movement of the controller computing device 1430. While theself-propelled device is moved, the controller computing device displayscontent that includes both virtual objects 1432 and the representation1434 of the self-propelled device. Based on the rules and object of thegame, the user can steer the self-propelled device and cause the virtualrepresentation 1434 to move on the screen in a manner that reflects thereal movement of the self-propelled device. As noted in FIG. 14A, eventssuch as collisions between the self-propelled device 1430 and itsenvironment, can be communicated and represented with the virtualrepresentation 1434 and its environment. Likewise, events that occurbetween the virtual representation 1434 and the virtual environment(e.g., wall or zombie collision) can be communicated and implemented onthe self-propelled device 1402 (e.g., the device may veer left).

FIG. 15 illustrates an interactive application that can be implementedfor use with multiple self-propelled devices, depicted as spherical orrobotic balls, under an embodiment. In FIG. 15, system 1500 creates anad-hoc network to arrange a number of self-propelled robotic balls intoa desired pattern on a planar surface 1515. For example, the balls maybe automatically arranged into a character, word, logo, or othermeaningful or visually interesting arrangement. Five robotic balls 1510,1512, 1514, 1516, and 1518 are shown for illustration, but this does notimply any limit to the number of robotic ball devices that can beincluded.

Video camera 1502 captures images of the robotic balls on surface 1515and relays the image to computer/controller 1506 using data link 1504.Computer/controller 1506 executes an application designed to identifythe robotic balls and instruct each robotic ball in moving to itsdesired position. Computer controller 1506 forms an ad-hoc network vialink 1506 with robotic balls 1510, 1512, 1514, 1516, and 1518 to sendinstructions to each ball. Link 1506 can, in one embodiment, be a linkto a single ball, and each ball is communicated with in turn. In anotherembodiment, link 1506 connects to two or more of the robotic balls, oris a broadcast channel to all robotic balls.

One task controller 1506 performs is identification of each ball and itslocation. To perform this task, in one embodiment controller 1506sequentially instructs each ball to emit a unique signal detectable bycamera 1502 in conjunction with controller 1506 and associatedapplication software. The signal may be detectable by a human or not.For example, a ball 1510 emits a certain color or pattern of light. Inone embodiment, the ball's light pattern is modulated in a mannerdetectable by video camera 1502 and controller 1506. In anotherembodiment, every ball in the array is instructed to simultaneously emitits own unique identification signal or light pattern.

Once every robotic ball on surface 1515 has been identified and locatedby controller 1506, controller 1506 issues a set of movementinstructions to each robotic ball to move it into the desired location.

FIGS. 16A and 16B illustrate a method of collision detection, accordingto an embodiment. In FIG. 16A, collision event 1600 occurs whenself-propelled device 1602 collides with fixed object 1604. A collisionevent causes a sudden negative acceleration in self-propelled device1602. Device 1602, in one embodiment, is equipped with multi-axisaccelerometers for sensing acceleration. The data from the accelerometersensors show a distinctive pattern indicating a collision event hasoccurred. In one embodiment, collision detection occurs in onboardprocessing of device 1602. If self-propelled device 1602 has establisheda network connection with another device, either a controller or anotherself-propelled device, then collision detection can occur in anyconnected device.

FIG. 16B shows a more complex case of a collision event 1620 between twoself-propelled devices 1622 and 1624. In the event of a collisionbetween two self-propelled devices, it may be the case that one was inmotion or that both were in motion, prior to the collision. Detection ofa collision between two self-propelled devices requires that a processorreceive data from both devices, and that the data be tagged to allowtime-correlation of collision events. If two collision events occur atthe nearly the same time in two self-propelled devices, it is inferredthat the two devices were involved in a collision event—they collidedwith each other. Further filtering is possible, for example to determineif the two devices were in close proximity, or if either was movingtoward the other at the time the collision event was detected. Filteringincreases the probability of accurately detecting a collision event fromacceleration data. Collision detection can be useful in games and inapplications that require detection of walls and obstacles.

CONCLUSION

One or more embodiments described herein provide that methods,techniques and actions performed by a computing device are performedprogrammatically, or as a computer-implemented method. Programmaticallymeans through the use of code, or computer-executable instructions. Aprogrammatically performed step may or may not be automatic.

One or more embodiments described herein may be implemented usingprogrammatic modules or components. A programmatic module or componentmay include a program, a subroutine, a portion of a program, or asoftware component or a hardware component capable of performing one ormore stated tasks or functions. As used herein, a module or componentcan exist on a hardware component independently of other modules orcomponents. Alternatively, a module or component can be a shared elementor process of other modules, programs or machines.

Furthermore, one or more embodiments described herein may be implementedthrough the use of instructions that are executable by one or moreprocessors. These instructions may be carried on a computer-readablemedium. Machines shown or described with FIGs below provide examples ofprocessing resources and computer-readable mediums on which instructionsfor implementing embodiments of the invention can be carried and/orexecuted. In particular, the numerous machines shown with embodiments ofthe invention include processor(s) and various forms of memory forholding data and instructions. Examples of computer-readable mediumsinclude permanent memory storage devices, such as hard drives onpersonal computers or servers. Other examples of computer storagemediums include portable storage units (such as CD or DVD units), flashmemory (such as carried on many cell phones and personal digitalassistants (PDAs)), and magnetic memory. Computers, terminals, networkenabled devices (e.g., mobile devices such as cell phones) are allexamples of machines and devices that utilize processors, memory andinstructions stored on computer-readable mediums. Additionally,embodiments may be implemented in the form of computer-programs, or acomputer usable carrier medium capable of carrying such a program.

Although illustrative embodiments have been described in detail hereinwith reference to the accompanying drawings, variations to specificembodiments and details are encompassed by this disclosure. It isintended that the scope of the invention is defined by the followingclaims and their equivalents. Furthermore, it is contemplated that aparticular feature described, either individually or as part of anembodiment, can be combined with other individually described features,or parts of other embodiments. Thus, absence of describing combinationsshould not preclude the inventor(s) from claiming rights to suchcombinations.

While certain embodiments of the inventions have been described above,it will be understood that the embodiments described are by way ofexample only. Accordingly, the inventions should not be limited based onthe described embodiments. Rather, the scope of the inventions describedherein should only be limited in light of the claims that follow whentaken in conjunction with the above description and accompanyingdrawings.

What is claimed is:
 1. A computer-implemented method performed by one ormore processors of a self-propelled spherical device, thecomputer-implemented method comprising: (a) receiving, from a mobilecomputing device, motion-sensed inputs corresponding to a set of actionsperformed by a user of the mobile computing device, the motion-sensedinputs corresponding to the user's manipulation of the mobile computingdevice through a sensor set that can detect the mobile computing devicemoving in three-dimensional space, the sensor set including at least anaccelerometer; (b) interpreting the motion-sensed inputs as a set ofcommands according to instructions executable by the one or moreprocessors to maneuver the self-propelled spherical device, theexecutable instructions including motion input instructions specific tointerpreting the user's manipulation of the mobile computing devicethrough the sensor set; and (c) implementing the set of commands on adrive system of the self-propelled spherical device to maneuver theself-propelled spherical device in accordance with the executableinstructions; and (d) controlling the self-propelled spherical device.2. The method of claim 1, wherein the set of actions include at leastone action that has an inherent directional characteristic, and wherein(c) includes interpreting the at least one action as a directionalcommand and maneuvering the self-propelled spherical device, based onthe directional command, in a manner that is not correlative of theinherent directional characteristic of the at least one action.
 3. Themethod of claim 2, wherein the directional command causes theself-propelled spherical device to maneuver linearly in a firstdirection that is not correlative of the inherent directionalcharacteristic of the at least one action.
 4. The method of claim 2,wherein the directional command causes the self-propelled sphericaldevice to maneuver in multiple directions, including in at least onedirection that is not correlative of the inherent directionalcharacteristic of the at least one action.
 5. The method of claim 2,wherein the directional command causes the self-propelled sphericaldevice to maneuver in at least one rotational direction that is notcorrelative of the inherent directional characteristic of the at leastone action.
 6. The method of claim 1, wherein the executableinstructions, when executed, cause the self-propelled spherical deviceto control a direction, a velocity, a rotational motion, or a path ofthe self-propelled spherical device.
 7. The method of claim 1, whereinthe set of actions performed by the user include a touch input that isindicative of a first direction, and wherein (c) includes interpretingthe touch input as a directional command and maneuvering theself-propelled spherical device in at least a second direction that isdifferent than the first direction in accordance with the directionalcommand.
 8. The method of claim 1, wherein (a) includes receiving adirectional motion input corresponding to the user moving the mobilecomputing device in a manner that is indicative of a first direction,and wherein (c) includes interpreting the directional motion input as adirectional command and maneuvering the self-propelled spherical devicein at least a second direction that is different than the firstdirection in accordance with the directional command.
 9. The method ofclaim 1, wherein the set of actions includes a first type of action thatis detected by a first mechanism of the mobile computing device, andwherein the user moving the mobile computing device is detected by asecond mechanism of the mobile computing device, and wherein theexecutable instructions include instructions to maneuver theself-propelled spherical device in accordance with the first type ofaction and the user's manipulation of the mobile computing devicethrough the sensor set.
 10. The method of claim 9, wherein the firstmechanism corresponds to a first sensor in the sensor set of the mobilecomputing device, and the second mechanism corresponds to theaccelerometer of the mobile computing device.
 11. The method of claim 9,wherein the first type of action corresponds to the user touching one ormore regions of a surface of the mobile computing device.
 12. The methodof claim 1, wherein the set of actions includes the user manipulatingthe mobile computing device through the sensor set while simultaneouslyperforming a second action, and wherein the set of commands includes acommand to further maneuver the self-propelled spherical device inaccordance with the second action.
 13. The method of claim 12, whereinthe second action corresponds to the user maintaining a position of oneor more fingers on a display screen of the mobile computing device. 14.The method of claim 1, wherein the set of actions includes a promptedaction corresponding to a generated user-prompt on a display of themobile computing device, and wherein the set of commands includes acommand to maneuver the self-propelled spherical device at leastpartially in accordance with the prompted action.
 15. The method ofclaim 14, wherein the generated user prompt specifies the user toposition a hand or finger on a specified area of the display.
 16. Themethod of claim 1, wherein the user's manipulation of the mobilecomputing device through the sensor set corresponds to a simulated golfstroke using the mobile computing device, and wherein the set ofcommands cause the self-propelled spherical device to maneuver in amanner that simulates a golf ball that is directed by the simulated golfstroke.
 17. The method of claim 1, wherein the user's manipulation ofthe mobile computing device through the sensor set corresponds to asimulated bowling stroke, and wherein the set of commands cause theself-propelled spherical device to maneuver in a manner that simulates abowling ball that is directed by the simulated bowling stroke.
 18. Themethod of claim 1, wherein the instructions executable by the one ormore processors to maneuver the self-propelled spherical device includespecified instructions corresponding to the user moving the mobilecomputing device linearly, in an arc, and rotationally, and whereinexecution of the specified instructions causes the self-propelledspherical device to maneuver in accordance with the user moving themobile computing device linearly, in an arc, and rotationally.
 19. Asystem comprising: a mobile computing device configured to detect a setof actions performed by a user operating the mobile computing device;and a self-propelled spherical device in communication with the mobilecomputing device to: receive motion sensed inputs corresponding to theset of actions, the motion sensed inputs corresponding to the user'smanipulation of the mobile computing device through a sensor set thatcan detect the mobile computing device moving in three-dimensionalspace, the sensor set including at least an accelerometer; interpret theset of actions as a set of commands according to executable instructionsfor maneuvering the self-propelled spherical device, the executableinstructions including motion input instructions specific tointerpreting the user's manipulation of the mobile computing devicethrough the sensor set; implement the set of commands on a drive systemof the self-propelled spherical device to maneuver the self-propelledspherical device in accordance with the executable instructions; andcontrol the self-propelled spherical device.
 20. A computer-implementedmethod performed by one or more processors of a mobile computing device,the computer-implemented method comprising: (a) detecting a set ofactions performed by a user on the mobile computing device, the set ofactions including a first action in which the user manipulates themobile computing device through a sensor set that can detect the mobilecomputing device moving in three-dimensional space, the sensor setincluding at least an accelerometer; (b) interpreting the set of actionsas a set of commands according to instructions executable by the mobilecomputing device for maneuvering the self-propelled spherical device,the executable instructions including motion input instructions specificto interpreting the first action; (c) transmitting the set of commandsto the self-propelled spherical device to cause the self-propelledspherical device to maneuver in accordance with the executableinstructions; and (d) remotely controlling the self-propelled sphericaldevice.
 21. The method of claim 20, wherein the first action correspondsto an arc motion, pivot, or linear movement of the mobile computingdevice by the user.
 22. The method of claim 20, wherein the first actioncorresponds to the user holding the self-propelled spherical devicewhile turning or walking.